Skip to content
This repository was archived by the owner on Nov 24, 2025. It is now read-only.

Fix incorrect VNC information#4272

Merged
ocket8888 merged 1 commit into
apache:masterfrom
shamrickus:master
Jan 9, 2020
Merged

Fix incorrect VNC information#4272
ocket8888 merged 1 commit into
apache:masterfrom
shamrickus:master

Conversation

@shamrickus

@shamrickus shamrickus commented Jan 9, 2020

Copy link
Copy Markdown
Member

What does this PR (Pull Request) do?

  • This PR is not related to any Issue

Which Traffic Control components are affected by this PR?

  • Documentation

What is the best way to verify this PR?

Build docs and confirm vnc connection works using CIAB

If this is a bug fix, what versions of Traffic Control are affected?

The following criteria are ALL met by this PR

  • This PR includes tests OR I have explained why tests are unnecessary
  • This PR includes documentation OR I have explained why documentation is unnecessary
  • This PR includes an update to CHANGELOG.md OR such an update is not necessary
  • This PR includes any and all required license headers
  • This PR ensures that database migration sequence is correct OR this PR does not include a database migration
  • This PR DOES NOT FIX A SERIOUS SECURITY VULNERABILITY (see the Apache Software Foundation's security guidelines for details)

Additional Information

@ocket8888 ocket8888 added bug something isn't working as intended cdn-in-a-box related to the Docker-based CDN-in-a-Box system documentation related to documentation low impact affects only a small portion of a CDN, and cannot itself break one labels Jan 9, 2020
@ocket8888 ocket8888 self-assigned this Jan 9, 2020

@ocket8888 ocket8888 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Builds without error or warning, looks fine, accurate to the actual exposed port

@ocket8888
ocket8888 merged commit 0c04aac into apache:master Jan 9, 2020
alias mydc="docker-compose -f $PWD/docker-compose.yml -f $PWD/optional/docker-compose.vnc.yml"
alias mydc="docker-compose "` \
`"-f $PWD/docker-compose.yml "` \
`"-f $PWD/docker-compose.expose-ports.yml "` \

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

docker-compose.expose-ports.yml is not necessary for VNC.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How would you access the VNC service if the port is kept internal to the Docker network?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oh, you mean you don't need expose the other ports. Yeah, I guess that's true.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

bug something isn't working as intended cdn-in-a-box related to the Docker-based CDN-in-a-Box system documentation related to documentation low impact affects only a small portion of a CDN, and cannot itself break one

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants